Systems and method for providing a data security service

ABSTRACT

Systems, methods, and computer-readable media for providing standards compliant encryption, storage, and retrieval of data are disclosed. In an embodiment, data is received at a first data center from a first device in connection with a service request and encrypted to produce encrypted data. The encrypted data may be transmitted from the first data center to the first device, and then may subsequently be received at a second data center. The second data center may store the encrypted data in a database accessible to the second data center. Because all data provided to the system is encrypted by the first data center prior to being stored and/or provided to the second data center, the database and the second data center may be out of the scope of compliance monitoring, auditing, and reporting for one or more data security standards.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/841,021, filed Apr. 6, 2020, entitled SYSTEMS AND METHOD FORPROVIDING A DATA SECURITY SERVICE, which is a continuation of U.S.patent application Ser. No. 15/965,454, filed Apr. 27, 2018, entitledSYSTEMS AND METHOD FOR PROVIDING A DATA SECURITY SERVICE, which is acontinuation of U.S. patent application Ser. No. 14/991,533, filed Jan.8, 2016, entitled SYSTEMS AND METHOD FOR PROVIDING A DATA SECURITYSERVICE, the disclosures of which are incorporated by reference hereinin their entirety.

TECHNICAL FIELD

This invention relates to systems and methods for encryption and storageof data, and more particularly to improving systems and methods forproviding standards compliant encryption, storage, and retrieval ofdata.

BACKGROUND

The use of web-based systems has proliferated for many years, and as theuse of web-based systems has grown, so too has the amount of data thatis communicated between end-users and the web-based systems. The datacommunicated between the end-users and the web-based systems oftenincludes sensitive information (e.g., credit card numbers, bank accountnumbers, social security numbers, driver's license numbers, etc.). Manyweb-based systems retain this sensitive information for variouspurposes. For example, some e-commerce websites store user credit cardinformation so that the user does not have to provide that informationeach time they perform a transaction with the e-commerce website.

Various data security techniques and protocols have been developed toprotect sensitive user data from exposure to unauthorized third parties.One such protocol is the payment card industry data security standard(PCI DSS) which was developed to increase controls for protectingcardholder data and to reduce credit card fraud caused by unauthorizedexposure of the cardholder data. The PCI DSS defines various safeguardsand data protection methods that should be used by entities thatprocess, store, and/or transmit financial card information. Whilecompliance with PCI DSS is not mandated by federal laws, many stateshave either referenced the PCI DSS, made equivalent provisions, orincorporated the PCI DSS into state law. Further, compliance with thePCI DSS may shield entities that process cardholder data from liabilityin the event that the cardholder data is breached (e.g., accessed by anunauthorized third party).

For many entities, establishing PCI DSS compliance can be a costly andtime consuming process. For example, a user may enter cardholder data(e.g., credit card number, expiration date, control verification value(CVV), etc.) into a form on a website using an electronic device, suchas a smart phone, tablet computing device, or other personalcomputer/laptop. When the user submits the form the cardholder data maybe encrypted using transport layer security (TLS) and transmitted to aweb server via a hypertext transfer protocol secure (HTTPS)communication link. Upon receiving the cardholder information, the webserver may invoke an application programming interface (API) call thatprocesses the cardholder information to facilitate a transaction. Inaddition to processing the cardholder information, the API call maycreate a log entry that includes at least a portion of the cardholderdata, and the log may be written to storage. When the cardholderinformation is stored in the log entry, the cardholder data becomes atrest data (e.g., stored data), and any systems accessing and/or storingthe at rest data may be subject to monitoring, auditing, and reportingfor compliance with the PCI DSS. For example, when the web server storesthe cardholder information at a data center, both the web server and thedata center may be subject to PCI DSS compliance monitoring, auditing,and reporting to verify that the cardholder information has not beenstored in an unprotected format (e.g., as unencrypted data). As thenumber of systems accessing the data center increases, the scope andcost of PCI DSS compliance monitoring, auditing, and reporting may alsoincrease.

Compliance monitoring, auditing, and reporting is further complicatedand becomes more costly when techniques used for compliance monitoring,auditing, and reporting are performed statically. That is, when a systemis configured to perform monitoring, auditing, and reporting in acertain way based on a current state of the relevant compliance standard(e.g., PCI DSS), changes to the compliance standard may require that theentire monitoring, auditing, and reporting protocols implemented by thesystem, as well as safeguards, such as when, where, and how data isstored, be retooled/reprogrammed, etc. to ensure compliance under themodified compliance standard. This further increases the costs ofmonitoring, auditing, and reporting for compliance purposes.

SUMMARY

The present disclosure is directed to embodiments of systems, methods,and computer-readable storage media for encryption and storage of datausing multiple data centers that provides a simple, dynamic, andscalable solution for compliance monitoring, auditing, and reportingprocesses, and that reduces the costs of implementing the compliancemonitoring, auditing, and reporting processes. In an embodiment a firstdata center provides for encryption and decryption of sensitive datautilizing a compliant protocol standard. The encrypted data generated bythe first data center is then provided back the appropriate device, andthe device may then communicate the encrypted data to a second datacenter that provides business logic for providing one or more servicesto a user of the device based on the encrypted data. The second datacenter may include a database that may store the encrypted data. When adevice needs to access the data (e.g., in either an encrypted orunencrypted format), the device may communicate a request for the datato the first data center, and the first data center may retrieve therequested data in an encrypted format from the database of the seconddata center. If the data is requested in an encrypted format, the datamay be retrieved and communicated to the end-point device by the firstdata center without decrypting the data. If the data is requested in anunencrypted format, the data may be retrieved and decrypted by the firstdata center prior to being communicated from the first data center tothe end-point device. Thus, all unencrypted data is processed by thefirst data center, and all information provided to, or retrieved from,the second data center is encrypted according to the appropriatecompliance monitoring, auditing, and reporting standard, such as the PCIDSS.

Compliance monitoring, auditing, and reporting processes for systemsconfigured according to embodiment may be simplified in many ways. Forexample, only the first data center may be subject to compliancemonitoring, auditing, and reporting because all unencrypted dataentering or leaving the system flows through the first data center only(i.e., the second data center does not receive or store unencrypteddata). Further, because the first data center does not include adatabase store user data, the risk of unencrypted data being stored atrest may be eliminated or at least greatly reduced. Additionally, thesecond data center may be outside of the scope of the compliancemonitoring, auditing, and reporting process because all data stored inthe database of the second data center is stored in a compliantencryption format, thereby eliminating the risk that unencrypted data isstored at rest in the database of the second data center.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the invention that follows may be better understood.Additional features and advantages of the invention will be describedhereinafter which form the subject of the claims of the invention. Itshould be appreciated by those skilled in the art that the conceptionand specific embodiment disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present invention. It should also be realized by thoseskilled in the art that such equivalent constructions do not depart fromthe spirit and scope of the invention as set forth in the appendedclaims. The novel features which are believed to be characteristic ofthe invention, both as to its organization and method of operation,together with further objects and advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. It is to be expressly understood, however, thateach of the figures is provided for the purpose of illustration anddescription only and is not intended as a definition of the limits ofthe present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, reference isnow made to the following descriptions taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram illustrating aspects of an embodiment of asystem for providing standards compliant encryption, storage, andretrieval of data;

FIG. 2 is a block diagram illustrating additional aspects of anembodiment of a system for providing standards compliant encryption,storage, and retrieval of data; and

FIG. 3 is a flow chart of an embodiment of a method for providingstandards compliant encryption, storage, and retrieval of data.

DETAILED DESCRIPTION

Various features and advantageous details are explained more fully withreference to the non-limiting embodiments that are illustrated in theaccompanying drawings and detailed in the following description.Descriptions of well-known starting materials, processing techniques,components, and equipment are omitted so as not to unnecessarily obscurethe invention in detail. It should be understood, however, that thedetailed description and the specific examples, while indicatingembodiments of the invention, are given by way of illustration only, andnot by way of limitation. Various substitutions, modifications,additions, and/or rearrangements within the spirit and/or scope of theunderlying inventive concept will become apparent to those skilled inthe art from this disclosure.

Referring to FIG. 1 , a block diagram illustrating aspects of anembodiment of a system for providing standards compliant encryption,storage, and retrieval of data is shown as a system 100. As shown inFIG. 1 , the system 100 includes a data center 110, a data center 130, adatabase 150, a firewall 160, and firewalls 180, 190. The system 100 maybe communicatively coupled to an electronic device 140 and an end-pointdevice 170 via one or more networks (not shown in FIG. 1 ). It is notedthat although FIG. 1 illustrates a single electronic device 140 and asingle end-point 170, systems configured according to embodiments of thepresent disclosure, such as the system 100 of FIG. 1 , may becommunicatively coupled to more than one electronic device 140 and/ormore than one end-point device 170. Further, some systems configuredaccording to embodiments of the present disclosure, such as the system100 of FIG. 1 , may not be communicatively coupled to an electronicdevice 140 or may not be communicatively coupled to an end-point device170. Thus, embodiments of the present disclosure should not be limitedto a particular number of electronic devices 140 and end-point devices170.

As illustrated in FIG. 1 , the data center 110 includes a processor 112,a memory 114, a security service 118, an encryption/decryption service120, and a proxy 122. In an embodiment, the memory 114 may storeinstructions 116 that, when executed by the processor 112, cause theprocessor 112 to perform the operations described with respect to thedata center 110 with reference to FIGS. 1-3 . For example, theinstructions 116 may include instructions that, when executed by theprocessor 112, cause the processor 112 to provide the security service118 and/or the encryption/decryption service 120. In an embodiment, thesecurity service 118 may be configured to encrypt data received from theelectronic device 140 and/or the end-point device 170, to provide theencrypted data to the electronic device 140 and/or the end-point device170, and/or to decrypt encrypted data that is retrieved from the datacenter 130, as described in more detail below. In an embodiment, theencryption provided by the security service 118 may include tokenizationof the data. In an additional or alternative embodiment, the encryptionprovided by the security service 118 may comply with one or more datasecurity standards, such as the PCI DSS. In an embodiment, theencryption/decryption service 120 may be configured to manage encryptionand decryption keys that are utilized by the security service 118 toencrypt and decrypt data, as described in more detail below. In anembodiment, the proxy 122 may provide an interface that allows theend-point device 170 to access functionality of the system 100, such asfor providing data to, or retrieving data from, the system 100, asdescribed in more detail below. In an embodiment, the data center 110does not include a database for storing user data.

The data center 130 includes a processor 132, a memory 134, and backendservices 138. In an embodiment, the memory 134 may store instructions136 that, when executed by the processor 132, cause the processor 132 toperform the operations described with respect to the data center 130with reference to FIGS. 1-3 . For example, the instructions 136 mayinclude instructions that, when executed by the processor 132, cause theprocessor 132 to provide the backend services 138. In an embodiment, thebackend services 138 may be provided to users, such as a user of theelectronic device 140 and/or an entity associated with the end-pointdevice 170, and may utilize data that has been encrypted by the datacenter 110, as described in more detail below. In an embodiment, thebackend services 138 may be facilitated by one or more applicationprogramming interfaces (APIs). In an embodiment, the data center 130 mayprovide business logic configured to provide the backend services 138 toa user of the electronic device 140. The one or more backend services138 may utilize user data that has been encrypted by the data center110. In an embodiment, the backend services 138 provided by the businesslogic may include a money transfer service, a prepaid card loadingservice, a bill pay service, an e-commerce service, or a combinationthereof. In an embodiment, the data center 130 does not includedecryption and encryption functionality. Thus, in some embodiments, thedata center 130 may be incapable of decrypting and/or altering theencrypted data received from, or provided to various external devices,such as the electronic device 140, the end-point device 170, and thedata center 110.

As shown in FIG. 1 , the electronic device 140 includes a processor 142and a memory 144. In an embodiment, the memory 144 may storeinstructions 146 that, when executed by the processor 142, cause theprocessor 142 to perform the operations described in connection with theelectronic device 140 with reference to FIGS. 1-3 . In an embodiment,the electronic device 140 may be operated by the same entity thatoperates the data centers 110, 130. For example, in an embodiment, thedata centers 110, 130 may be operated by a money transfer networkentity, and the electronic device 140 may be a kiosk operated by themoney transfer network entity (e.g., at a money transfer agent location,a retail store location, etc.). In an additional or alternativeembodiment, the electronic device 140 may be a user device, such as asmart phone, personal digital assistant, laptop computing device, tabletcomputing device, and the like, that is operated by an individual otherthan the entity providing the data centers 110, 130. For example, in anembodiment, the electronic device 140 may be a smart phone that includesan application (e.g., stored as the instructions 146) that is used toprovide one or more services to the user of the electronic device 140.The application may communicate with the data centers 110, 130 toprovide a service (e.g., a money transfer service, a prepaid cardloading service, and the like) to the user, as described in more detailbelow. As illustrated in FIG. 1 , in an embodiment, the electronicdevice 140 may be communicatively coupled to the data center 110 via afirst secure communication link (e.g., the communication linkfacilitated by the firewall 180), and the electronic device 140 may becommunicatively coupled to the data center 130 via a second securecommunication link (e.g., the communication link facilitated by thefirewall 190).

In an embodiment, the end-point device 170 may be a point of sale system(POS) that communicates with the data center 130 via the proxy 122 inconnection with utilizing one or more of the backend services 138, asdescribed in more detail below. In an additional or alternativeembodiment, the end-point device 170 may be a portal that interfaces thedata centers 110, 130 to a third party system. For example, theend-point device 170 may be a portal that interfaces the data centers110, 130 with a credit card processing system (e.g., a portal forprocessing Visa® credit card payments). In still another additional oralternative embodiment, the end-point device 170 may be a web-server,such as a web-server that provides online shopping services toconsumers.

During operation, a user may use the electronic device 140 and/or theend-point device 170 to access a service (e.g., one of the backendservices 138) provided by an operator of the data centers 110, 130. Theservice may require that the user provide various information that isrelevant to the accessed service. Depending on the service, the dataprovided by the user may include sensitive data, such as a credit cardinformation, driver's license information, passport information, bankaccount information, and the like. When the information provided inconnection with the service includes sensitive data, the electronicdevice 140 and/or the end-point device 170 may be configured to transmitthe sensitive information to the data center 110. The data center 110may be configured to encrypt the sensitive data (e.g., using thesecurity service 118 and the encryption/decryption service 120) toproduce encrypted data, and the data center 110 may then transmit theencrypted data back to the electronic device 140 and/or the end-pointdevice 170. In an embodiment, the data center 110 may encrypt the datausing tokenization, and the encrypted data may be a token that isgenerated by the tokenization. In an embodiment, the data center 110 maybe configured to not store the sensitive data at rest.

The electronic device 140 and/or the end-point device 170 may receivethe encrypted data from the data center 110, and may transmit theencrypted data to the data center 130 in connection with accessing theone or more backend services 138. For example, when the service is anonline purchase, the encrypted data may take the form of a tokengenerated from credit card information, and the backend service accessedby the electronic device 140 and/or the end-point device 170 mayfacilitate processing of the purchase (e.g., using the token withouthaving to receive the sensitive data). In an embodiment, the encrypteddata may be stored as an entry in the database 150. For example, theaccessed service may generate a log of transactions, and the log mayinclude the encrypted data processed during each of the transactions.Because the data center 130 only receives encrypted data, and becausethe database 150 only stores encrypted data, the data center 130 and thedatabase 150 may be outside the scope of compliance auditing for variouspurposes/standards. For example, the data center 130 and database 150 ofembodiments may be outside the scope of PCI DSS monitoring, auditing,and reporting because sensitive information is never stored at the datacenter 130 and the database 150 in an unencrypted format. Thus, in thesystem 100 illustrated in FIG. 1 , only the data center 110 may besubject to PCI DSS monitoring, auditing, and reporting. This may greatlyreduce the costs associated with implementing PCI DSS compliancemonitoring, auditing, and reporting. Further, it is noted that theconfiguration illustrated in FIG. 1 may reduce the scope of compliancemonitoring, auditing, and reporting for data security standards and datasecurity protocols other than the PCI DSS.

Further, when a device (e.g., the electronic device 140 and/or theend-point device 170) desires to access the encrypted information, thedevice may transmit a request to the data center 110. In an embodiment,the request may be provided to the proxy 122, and the proxy 122 maycommunicate with the data center 130 through the firewall 160 via asecure connection such an https connection, a virtual private networkconnection or other form of network communication, to retrieve therequested data from the database 150. The requested data (e.g., in anencrypted format) may be retrieved from the database 150, and may beprovided from the data center 130 to the data center 110 through thefirewall 160 via a secure connection such an https connection, a virtualprivate network connection or other form of network communication, andthe data center 110 may either: 1) decrypt the data and provide thedecrypted data to the device; or 2) provide the encrypted data to thedevice. From the foregoing it is shown that all data provided to, orretrieved from, the data center 130 is in an encrypted format, and thatdecrypted data is only provided to, or provided from, the system 100 viathe data center 110, which encrypts all incoming data (e.g., data to bestored or otherwise provided to the data center 130), and may decryptsome, but not necessarily all, outgoing data (e.g., data retrieved fromthe data center 130). Additional aspects of embodiments for processingdata and providing services are described below with reference to FIGS.1-3 .

In an embodiment illustrative of a first exemplary mode of operation forthe system 100, the electronic device 140 may be a kiosk device operatedby, or a mobile application provided by, a money transfer networkentity. The money transfer network entity may also operate the datacenter 110 and the data center 130. The end-point device 170 may be aportal to a system operated by a credit card provider, a money transferagent device located at a money transfer agent location, a web server,etc. During operation, a user may access the electronic device 140, and,using one or more graphical user interfaces (GUIs) presented by theelectronic device 140, the user may provide information in connectionwith requesting a particular service (e.g., one of the backend services138), such as a money transfer transaction, loading a prepaid card, abill pay service, and the like. The one or more GUIs may prompt the userto enter various user data 102, which may include sensitive information.Rather than providing the user data 102 to the data center 130, and moreparticularly, the one or more backend services 138, the electronicdevice 140 may be configured to transmit the user data 102 to the datacenter 110. In an embodiment, the user data 102 may only be transmittedto the data center 110 when the user data 102 includes sensitiveinformation. For example, the GUI may be programmed to determine whethera requested service requires the user to input sensitive information(e.g., credit card number, social security number, driver's licensenumber, passport number, bank account information, and the like), and,in response to a determination that the requested service utilizessensitive information, the electronic device 140 may transmit the userdata 102 to the data center 110. In an embodiment, the electronic device140 may be communicatively coupled to the data center 110 via a securecommunication link. For example, the electronic device 140 maycommunicate with the data center 110 using an HTTPS or other securityprotocol. In an embodiment, the communication link between theelectronic device 140 and the data center 110 may facilitated throughthe firewall 180.

The data center 110 may receive the user data 102 from the electronicdevice 140, and, in response to receiving the user data 102, the datacenter 110 may encrypt the user data 102 to produce encrypted data 104.In an embodiment, the user data 102 may be encrypted using tokenization,and the encrypted data 104 may be a token. In an embodiment, the userdata 102 may be included in a body of a message. In an embodiment, themessage may be a hypertext transfer protocol (HTTP) message, and thebody of the HTTP message may include the data that is to be encrypted bythe data center 110. In an embodiment, a header of the HTTP message mayinclude information that identifies the location of the data within thebody of the HTTP message. In an additional or alternative embodiment,the header of the HTTP message may include information that identifies adestination for the data, such that the data center 110 may provide theencrypted data 104 to the destination, rather than the electronic device140, as described in more detail with reference to FIG. 2 . In yetanother additional or alternative embodiment, the header of the HTTPmessage may include information that identifies a destination for thedata, such that the data center 110 may provide the encrypted data 104to both the destination and the electronic device 140.

After generating the encrypted data 104, the data center 110 maytransmit the encrypted data 104 to the electronic device 140 and/orother destination devices depending on a configuration of the message(e.g., a configuration of HTTP headers, etc.). In response to receivingthe encrypted data 104, the electronic device 140 may transmit theencrypted data 104 to the data center 130. In an embodiment, theencrypted data 104 may be transmitted to the data center 130 as arequest to access one of the backend services 138. In response toreceiving the encrypted data 104, the data center 130 may store theencrypted data 104 in the database 150. In an embodiment, the encrypteddata 104 may be stored in the database 150 as a result of processing byone or more of the backend services 138. For example, a user may accessthe electronic device 140 to perform a transaction, such as loadingfunds onto a prepaid card, where the loading of the funds is provided byone of the backend services 138. The user may provide the user data 102in response to prompts presented at the electronic device 140, and thenthe user data 102 may be communicated to the data center 110 forencryption and then the encrypted data 104 may be returned to theelectronic device 140. The electronic device 140 may then provide theencrypted data 104 to the backend service 138, which may use theencrypted data 104 to load value onto the prepaid card. As a result ofthe transaction, the backend service 138 may create an entry in thedatabase 150 that includes the encrypted data 104.

In an embodiment, access to the encrypted data stored at the database150 may be provided by the data center 110. For example, the end-pointdevice 170 may request access to the encrypted data 104 in connectionwith providing one of the backend services 138. In an embodiment, accessto the encrypted data 104 may be provided to the end-point device 170via the data center 110. The end-point device 170 may communicate arequest to the proxy 122 of the data center 110, where the requestindicates that the end-point device 170 is requesting access to theencrypted data 104. In response to receiving the request, the datacenter 110 may retrieve the encrypted data 104 from the database 150 ofthe data center 130. Upon receiving the encrypted data 104 from the datacenter 130 through the firewall 160 via a secure connection such anhttps connection, a virtual private network connection or other form ofnetwork communication, the data center 110 may decrypt the encrypteddata 104 to produce decrypted data 106, and may provide the decrypteddata 106 to the end-point device 170. The end-point device 170 may thenprocess the decrypted data 106 to complete the transaction provided bythe backend service 138. For example, in an embodiment, the end-pointdevice 170 may be a portal that provides access to a financial cardnetwork operated by a financial card provider. If the backend service138 accessed by the user of the electronic device 140 involvesprocessing a credit card payment, the user data 102 may includefinancial card information, and the encrypted data 104 may includeencrypted financial card information. The encrypted data 104 may beretrieved from the database 150 by the data center 110, and thenprovided from the data center 110 to the end-point device 170 forfurther processing (e.g., to complete the credit card payment). In anembodiment, the data center 110 may provide encrypted data 104 to theend-point device 170 without decrypting the encrypted data 104. In anadditional or alternative embodiment, the data center 110 may decryptthe encrypted data 104 to generate the decrypted data 106, and mayprovide the decrypted data 106 to the end-point device 170. Theend-point device 170 may then perform further processing of the data tofacilitate the transaction requested by the user and/or the backendservice 138. In an embodiment, the processing performed by the end-pointdevice 170 may generate data that is to be stored in the database 150.In such instances, the data may be provided to the data center 110 wherethe data may be encrypted and subsequently provided through the firewall160 via a secure connection such an https connection, a virtual privatenetwork connection or other form of network communication, to the datacenter 130 for storage in the database 150.

In an embodiment, the data center 110 may be monitored and periodicallyaudited to determine whether data that has been encrypted by the datacenter 110 has been stored (e.g., in an unencrypted format) at restwithin the data center 110. As explained above, in some embodiments, thedata center 110 may not include a database for storing user data. Thus,the likelihood that user data is stored at rest within the data center110 may be reduced or eliminated. This may increase the likelihood thatthe result of the monitoring and periodic auditing results in adetermination that the data center 110 is compliant with various dataprivacy/security standards, such as the PCI DSS. Further, from theforegoing it has been shown that the data center 130 does not receiveunencrypted sensitive user data, and that all sensitive user data storedin the database 150 is stored in an encrypted format. Additionally, insome embodiments, the data center 130 does not include decryptioncapabilities, and is therefore not capable of decrypting the sensitiveuser data stored in the database 150. This may prevent the data center130 from inadvertently storing sensitive user data at rest in anunencrypted format within the data center 130 and/or the database 150.Accordingly, the data center 130 and the database 150 may be outside thescope of compliance monitoring, auditing, and reporting for various dataprivacy/security standards, such as the PCI DSS, which may significantlyreduce the costs associated with implementing the compliance auditing,monitoring, and reporting, decrease the amount of time required toperform such tasks, and may increase the accuracy of such tasks.Further, the configuration of the system 100 shown in FIG. 1 may alsoprovide a solution that is more easily scaled to accommodate increasesin capacity. For example, if additional capacity for storing encrypteddata and/or providing additional backend services 138 is required, thedata center 130 and/or the database 150 may be expanded withoutexpanding the scope of compliance monitoring, auditing, and reportingfor various data privacy/security standards. Further, because the datacenter 110 does not store user data at rest, additional resources can beprovided at the data center 110 to provided increased capacity withoutsignificantly altering the compliance monitoring, auditing, andreporting processes for various data privacy/security standards. Thus,the configuration of the system 100 illustrated in FIG. 1 providesimprovements to the technical field of providing standards compliantencryption, storage, and retrieval of data.

Referring to FIG. 2 , a block diagram illustrating additional aspects ofembodiments of a system for providing standards compliant encryption,storage, and retrieval of data is shown. In FIG. 2 , the system 100 ofFIG. 1 is shown. Additionally, in FIG. 2 , various data flows are shownand illustrate how data may be passed to and from various portions ofthe system 100 in connection with one or more embodiments.

In a first exemplary data flow according to embodiments, the end-pointdevice 170 may send a request 210 to the data center 110 (e.g., via theproxy 122). In an embodiment, the request 210 may be a request to accessdata stored at the database 150. In response to receiving the request210, the data center 110 may forward or otherwise communicate therequest 210 to the data center 130 through the firewall 160 via a secureconnection such an https connection, a virtual private networkconnection or other form of network communication. The data center 130,in response to receiving the request 210 from the data center 110, maygenerate a query 212 and provide the query 212 to the database 150. As aresult of the query 212, encrypted data 214 may be retrieved from thedatabase 150, and the encrypted data 214 may then be provided from thedata center 130 to the end-point device 170 through the firewall 160 viaa secure connection such an https connection, a virtual private networkconnection or other form of network communication, and the data center110 as requested data 216. In an embodiment, the requested data 216 maybe the same as the encrypted data 214 (e.g., the data center 110 doesnot decrypt the encrypted data 214 prior to providing it to theend-point device 170). In an additional or alternative embodiment, therequested data 216 may be decrypted data generated at the data center110 by decrypting (e.g., using the security service(s) 118 and/or theencryption/decryption service(s) 120) the encrypted data 214. It isnoted that the decrypted data may not be provided to the data center130, thereby maintaining the data center 130 outside of the scope of thecompliance monitoring, auditing, and reporting processes.

In a second exemplary data flow according to embodiments, the electronicdevice 140 may send a request 220 to the data center 110. In anembodiment, the request 220 may be a request to access data stored atthe database 150. In response to receiving the request 220, the datacenter 110 may forward or otherwise communicate the request 220 to thedata center 130 through the firewall 160 via a secure connection such anhttps connection, a virtual private network connection or other form ofnetwork communication. The data center 130, in response to receiving therequest 220 from the data center 110, may generate a query 222 andprovide the query 222 to the database 150. As a result of the query 222,encrypted data 224 may be retrieved from the database 150, and theencrypted data 224 may then be provided from the data center 130 to theelectronic device 140 through the firewall 160 via a secure connectionsuch an https connection, a virtual private network connection or otherform of network communication, and the data center 110 as requested data226. In an embodiment, the requested data 226 may be the same as theencrypted data 214 (e.g., the data center 110 does not decrypt theencrypted data 224 prior to providing it to the end-point device 170).This may enable the electronic device 140 to access one or more of thebackend services 138 that may utilize the encrypted data 224 to providea service to a user of the electronic device 140. In an additional oralternative embodiment, the requested data 226 may be decrypted datagenerated at the data center 110 by decrypting (e.g., using the securityservice(s) 118 and/or the encryption/decryption service(s) 120) theencrypted data 224. It is noted that the decrypted data may not beprovided to the data center 130, thereby maintaining the data center 130outside of the scope of the compliance monitoring, auditing, andreporting processes.

In a third exemplary data flow according to embodiments, the electronicdevice 140 may send a request 230 to the data center 110. In anembodiment, the request 230 may be a request to process data stored atthe database 150. For example, the request 230 may be a request toconduct a transaction using financial card information that has beenpreviously stored at the database 150 in an encrypted format. In anembodiment, the request 230 may identify an address (e.g., an address ofa web server) where data retrieved from the database 150 in response tothe request 230 is to be provided. In response to receiving the request230, the data center 110 may forward or otherwise communicate therequest 230 to the data center 130 through the firewall 160 via a secureconnection such an https connection, a virtual private networkconnection or other form of network communication. The data center 130,in response to receiving the request 230 from the data center 110, maygenerate a query 232 and provide the query 232 to the database 150. As aresult of the query 232, encrypted data 234 may be retrieved from thedatabase 150, and the encrypted data 234 may then be provided from thedata center 130 to the end-point device 170 through the firewall 160 viaa secure connection such an https connection, a virtual private networkconnection or other form of network communication, and the data center110 as requested data 236. In an embodiment, the requested data 236 maybe the same as the encrypted data 214 (e.g., the data center 110 doesnot decrypt the encrypted data 234 prior to providing it to theend-point device 170). This may enable the electronic device 140 toaccess one or more of the backend services 138 that may utilize theencrypted data 224 to provide a service to a user of the electronicdevice 140 via one or more external systems (e.g., one or more externalsystems that communicate with the system 100 via the end-point device170). In an additional or alternative embodiment, the requested data 236may be decrypted data generated at the data center 110 by decrypting(e.g., using the security service(s) 118 and/or theencryption/decryption service(s) 120) the encrypted data 234. It isnoted that the decrypted data may not be provided to the data center130, thereby maintaining the data center 130 outside of the scope of thecompliance monitoring, auditing, and reporting processes.

FIG. 3 is a flow diagram of an embodiment of a method for providingstandards compliant encryption, storage, and retrieval of data is shownas a method 300. In an embodiment, the method 300 may be performed bythe system 100 of FIGS. 1 and 2 . In an embodiment, the method 300 maybe stored as instructions (e.g., one or more of the instructions 116,136, 146 of FIG. 1 ) that, when executed by a processor (e.g., one ormore of the processors 112, 132, 142 of FIG. 1 ), cause the processor toperform the operations of the method 300 to provide standards compliantencryption, storage, and retrieval of data in accordance with one ormore embodiments of the present disclosure.

At 310, the method 300 includes receiving data at a first data centerfrom a first device. In an embodiment, the first data center may be thedata center 110 of FIGS. 1 and 2 , and the first device may be theelectronic device 140 of FIGS. 1 and 2 . In an additional or alternativeembodiment, the first data center may be the data center 110 of FIGS. 1and 2 , and the first device may be the end-point device 170 of FIGS. 1and 2 . In an embodiment, the data may be received at the first datacenter in connection with a service request (e.g., a request to accessone of the backend services 138 of FIG. 1 ). At 320, the method 300includes encrypting the data at the first data center to produceencrypted data, and, at 330, transmitting the encrypted data from thefirst data center to the first device. The first device may receive theencrypted data from the first data center, and may transmit theencrypted data to a second data center. In an embodiment, the seconddata center may be the data center 130 of FIGS. 1 and 2 . At 340, thesecond data center may receive the encrypted data, and, at 350, maystore the encrypted data at a database accessible to the second datacenter. In an embodiment, the database may be the database 150 of FIGS.1 and 2 .

Subsequently, the method 300 may include, at 360, receiving, at thefirst data center, a request to access the encrypted data. In anembodiment, the request may be received in connection with providing aservice (e.g., one of the backend services 138 of FIG. 1 ) to a user. At370, the method 300 may include retrieving, by the first data center,the encrypted data from the database. In an embodiment, the first datacenter may communicate with the second data center to retrieve theencrypted information from the database, as described with reference toFIG. 2 . In an embodiment, the data retrieved at 370 may be provided, at390, from the first data center to a destination device. In anembodiment, the destination device may be the end-point device 170 ofFIGS. 1 and 2 . In an additional or alternative embodiment, thedestination device may be a remote system that is communicativelycoupled to the data centers via the end-point device 170. In stillanother additional or alternative embodiment, the destination device maybe the electronic device 140 of FIGS. 1 and 2 . In an embodiment, themethod 300 may include, at 380, decrypting the encrypted data retrievedat 370, and then, at 390, providing the decrypted data to thedestination device.

Although the present invention and its advantages have been described indetail, it should be understood that various changes, substitutions andalterations can be made herein without departing from the spirit andscope of the invention as defined by the appended claims. Moreover, thescope of the present application is not intended to be limited to theparticular embodiments of the process, machine, manufacture, compositionof matter, means, methods and steps described in the specification. Asone of ordinary skill in the art will readily appreciate from thedisclosure of the present invention, processes, machines, manufacture,compositions of matter, means, methods, or steps, presently existing orlater to be developed that perform substantially the same function orachieve substantially the same result as the corresponding embodimentsdescribed herein may be utilized according to the present invention.Accordingly, the appended claims are intended to include within theirscope such processes, machines, manufacture, compositions of matter,means, methods, or steps.

What is claimed is:
 1. A method for securely transmitting sensitive datain a computer network, the method comprising: receiving information froma graphic user interface (GUI) of an electronic user device, wherein theinformation may include sensitive data; determining, by the electronicuser device, if the received information contains sensitive data, and ifthe received information contains sensitive data, transmitting, by theelectronic user device, the sensitive data to a first data center;encrypting, by the first data center, the sensitive data to produceencrypted data without storing the sensitive data at rest; transmitting,by the first data center, the encrypted data to the electronic userdevice; transmitting, by the electronic user device, the encrypted datato a second data center; storing the encrypted data in a databaseaccessible to the second data center; transmitting, by the electronicuser device or an end-point device, a first request to the first datacenter to retrieve the encrypted data; transmitting, by the first datacenter, through a proxy to the second data center, a second request toretrieve the encrypted data from the database; retrieving, by the seconddata center, the encrypted data from the database in response to thesecond request; transmitting, by the second data center, the encrypteddata to the first data center; and transmitting, by the first datacenter, the sensitive data to the electronic user device or to theend-point device without encrypting the sensitive data.
 2. The method ofclaim 1, wherein the encrypting of the sensitive data utilizestokenization and the encrypted data is a token.
 3. The method of claim1, wherein the transmitting the sensitive data to the first data centeruses HTTPS.
 4. The method of claim 1, wherein the end-point deviceprocesses the sensitive data to complete a transaction provided by abackend service.
 5. The method of claim 4, wherein the backend serviceprocesses a credit card payment.
 6. The method of claim 4, wherein theprocessing by the end-point device generates additional data that is tobe stored in the database.
 7. The method of claim 1, wherein the secondrequest identifies a destination IP address for the encrypted dataretrieved from the database.